Skip to content

Update release guidance#7084

Open
NickColley wants to merge 1 commit into
mainfrom
update-release-guidance
Open

Update release guidance#7084
NickColley wants to merge 1 commit into
mainfrom
update-release-guidance

Conversation

@NickColley
Copy link
Copy Markdown
Contributor

Based on the changes made to the release process in the improve the release process epic

Closes #5674

Comment thread docs/releasing/publishing.md Outdated
@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 21, 2026

📋 Stats

No changes to any distributed file sizes!


Action run for 6f5b050

@NickColley NickColley force-pushed the update-release-guidance branch from 956bd82 to 8bd2974 Compare May 21, 2026 15:52
@NickColley NickColley force-pushed the update-release-guidance branch from 8bd2974 to 62409aa Compare May 22, 2026 08:30
@NickColley NickColley force-pushed the update-release-guidance branch from 62409aa to 5c0e700 Compare May 22, 2026 08:34
@NickColley NickColley marked this pull request as ready for review May 22, 2026 08:34
@NickColley NickColley force-pushed the update-release-guidance branch from 5c0e700 to 002a981 Compare May 22, 2026 09:09
Copy link
Copy Markdown
Member

@romaricpascal romaricpascal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks overall OK, but it looks like something changed the numbering of the ordered lists.


3. Select the ["RELEASE: Build release" workflow](https://github.com/alphagov/govuk-frontend/actions/workflows/build-release.yml), provide the new version of GOV.UK Frontend you are releasing and run the workflow on the `main` branch. This will build the release and generate a pull request to review the new build.
1. Select the [RELEASE: Build release workflow](https://github.com/alphagov/govuk-frontend/actions/workflows/build-release.yml) and run the workflow:
1. Set the **Use workflow from** select field to `main`.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

question Do we have a separate place we explain how to release from support branches? We may want to say:

Suggested change
1. Set the **Use workflow from** select field to `main`.
1. Set the **Use workflow from** select field to `main` or the `support/*` branch you're releasing from.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is explained in the introduction at the moment

Comment thread docs/releasing/publishing-a-preview.md Outdated
Comment on lines +29 to 33
We should update both internal and cross-government Slack channels:

- [GDS: govuk-design-system](https://gds.slack.com/archives/CAF8JA25U)
- [GDS: digital-service-platforms](https://gds.slack.com/archives/C01E20X06JK)
- [x-gov: govuk-design-system](https://ukgovernmentdigital.slack.com/archives/C6DMEH5R6)
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggestion Just noticed that this list is no longer up to date. @calvin-lau-sig7 the list is usually in the comms draft, would it be OK to say something like:

Suggested change
We should update both internal and cross-government Slack channels:
- [GDS: govuk-design-system](https://gds.slack.com/archives/CAF8JA25U)
- [GDS: digital-service-platforms](https://gds.slack.com/archives/C01E20X06JK)
- [x-gov: govuk-design-system](https://ukgovernmentdigital.slack.com/archives/C6DMEH5R6)
We should update both internal and cross-government Slack channels listed with the Slack message draft.

That'd be easier to maintain than having the list both here and in the comms drafts, possibly drifting appart with time.

We can fix that in a subsequent PR, though 😊

Based on the changes made to the release process in the
[improve the release process epic](#6676)

Co-authored-by: Calvin Lau <77630796+calvin-lau-sig7@users.noreply.github.com>
Co-authored-by: domoscargin <domoscargin@users.noreply.github.com>
Co-authored-by: Romaric Pascal <romaric.pascal@digital.cabinet-office.gov.uk>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Improve release documentation

3 participants